If this is going in the right direction, I can complete the other entries discussed in #1078.

• IgnoredAnnotations
• IgnoredEnvVars
• IgnoredLabels

Not sure if there is a notification about a draft. Could you give me a feedback, if this goes into the right direction, @brokenpip3?

Not sure if there is a notification about a draft. Could you give me a feedback, if this goes into the right direction, @brokenpip3?

yes sorry, will take a look asap!

Sorry if took me a while, the PR looks good as start, we can continue like this for the others :)
However f possible let's not add directly IgnoredVolumes or IgnoredXXXX but a more comprehensive struct like:

type JenkinsSpec struct {
	[...]
	Lifecycle JenkinsLifecycle `json:"lifecycle,omitempty"`
}

type JenkinsLifecycle struct {
	Ignore JenkinsLifecycleIgnore `json:"ignore,omitempty"`
}

type JenkinsLifecycleIgnore struct {
	IgnoredVolumes []string `json:"volumes,omitempty"`
	IgnoredEnvs []string `json:"envs,omitempty"`
	IgnoredAnnotations []string `annotations:"envs,omitempty"`
	IgnoredLabels []string `json:"labels,omitempty"`
}

so we can express it like that:

kind: Jenkins
metadata:
  name: example
spec:
  lifecycle:
    ignore:
      volumes:
        - /var/lib/jenkins/cache
        - /var/lib/jenkins/tmp
      envs:
       - FOOBAR

you can continue to adjust the unit tests and I can instead add the e2e tests for cover your changes, don't worry about that part, it's something I can complete.

thanks again for your contribution!

I have adapted your changes and implemented ignoring of annotations and volumes.